home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!girvan.demon.co.uk
- From: Allan Girvan <allan@girvan.demon.co.uk>
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: WB 3.0
- Date: Sat, 27 Jan 96 13:35:08 GMT
- Message-ID: <9601271335.AA000ri@girvan.demon.co.uk>
- References: <4eathg$1dq@metroux.metrobbs.com>
- X-NNTP-Posting-Host: girvan.demon.co.uk
- X-Newsreader: ADMaN 1.7 Copyright 1995 S.T.Brown
- X-Mail2News-Path: relay-4.mail.demon.net!post.demon.co.uk!girvan.demon.co.uk
-
- On Fri, 26 Jan 96, Fuller wrote:
-
- > I have heard that workbench 3.0 has a bug involving reopening workbench
- > after an application has closed it. This bug is suppose to involve the
- > priority of the application, if the priority is to high workbench won't
- > reopen properly causing you to have to reboot. A new commidity called
- > mcx243 is suppose to fix it but I got a vector warning from Virus Checker
- > so I killed the program. Can anyone help me?
-
- I used to get "The exec's IO vector has been changed" or something similar
- - I wouldn't worry about it.
-
- To prevent it happening you could try setting the "STARTPRI" tooltype in
- the VirusChecker icon to a lower value than the MCX icon, e.g.
-
- "STARTPRI=-1"
-
- (Having said that, I notice that neither of the icons actually has a
- STARTPRI on my system but I don't get the warning any more!)
-
- The theory is that you can set "STARTPRI" in each commodity's icon to
- control the order in which they're run from WBStartup. If MCX is started
- before VirusChecker then the changes to the vectors won't be noticed.
-
- Cheers,
-
-
- Allan.
- --
- | EMail - allan@girvan.demon.co.uk | Running on // You Know it |
- | Greetings from Glasgow, Scotland | AMIGA 1200 \X/ makes sense |
-